06 — Open sourceAGPL-3.0github.com/work90210Open by default

Read the code. Audit the claims.

Where Trelvio's code is open, it is AGPL-3.0 licensed. No dual-licensing, no open-core bait-and-switch.

§ 01 — Why AGPL-3.0

The licence is the guarantee.

The strongest copyleft licence available. Here's why it matters for institutional software.

01

No proprietary forks

Anyone deploying the software must make source available. No cloud provider can close what we've opened.

02

Improvements flow back

Modifications must be shared. Every improvement by any organisation benefits the entire user community.

03

Institutional continuity

If Trelvio ceases to exist, every institution can fork, hire maintainers, and continue.

04

Auditable security

When your users are investigators, "trust us" is not a security model. Read the code, verify the crypto.

§ 02 — Repositories

Four repositories, all public.

trelvio/vaultkeeper

Sovereign evidence management. Chain-of-custody engine, append-only audit, CRDT collaboration, witness protection.

ActiveRust / TypeScript→
trelvio/apifold

Unified API connectivity layer. Type-safe adapters for third-party service integration.

ActiveTypeScript→
trelvio/vke1-spec

VaultKeeper Evidence Exchange specification. Cryptographic federation for cross-institution evidence sharing.

DraftMarkdown / Protobuf→
trelvio/clerk-validator

Standalone chain-of-custody verification. Court clerks verify evidence integrity without VaultKeeper.

ActiveRust→
§ 03 — Contributing

How to contribute.

Developers, researchers, and institutional partners.

01

Read the contributing guide

Each repository includes CONTRIBUTING.md with setup, code standards, and PR guidelines.

02

Open an issue first

For non-trivial changes, discuss the approach before writing code. Saves time and ensures alignment.

03

Security disclosures

Email [email protected]. Do not open public issues. 90-day responsible disclosure policy.

04

Institutional testing

Want to pilot VaultKeeper? We provide dedicated support for institutional evaluation.

§ 04 — Source

Ready to inspect the code?